Method and Apparatus for Managing Data Center Using Web Services

ABSTRACT

Access of data center resources is provided by the present invention using stateless and stateful Web services. For stateless Web services, the present invention provides an invoker API that allows a client to invoke a specific resource and perform an operation on the resource. For stateful Web services, the present invention provides a Web Service Definition file that defines attributes and operations for data center resources. The client may access an instance of a Web service resource once an endpoint reference is obtained from the server. Since the resource instance is persistent, the client may invoke data center operations and manipulate the resource attributes accordingly.

CROSS REFERENCE TO RELATED APPLICATION

The present invention is related to the following application entitled“Method and Apparatus for Combining Resource Properties and DeviceOperations Using Stateful Web Services”, Ser. No. ______ attorney docketno. CA920040064US1, filed even date hereof. The above relatedapplication is assigned to the same assignee, and is incorporated hereinby reference.

BACKGROUND OF THE INVENTION

1. Technical Field

The present invention relates to an improved network data processingsystem. Particularly, the present invention relates to a method andapparatus for utilizing Web services in the network data processingsystem. Still more particularly, the present invention relates to amethod and apparatus for using Web services to manage data centeroperations in the network data processing system.

2. Description of Related Art

In recent years, the use of Web services has increased due to thepopularity of the World Wide Web. With Web services, businesses mayperform transactions with consumers or other businesses. A serviceprovider may publish available services on the Internet using Webservices for an end user to subscribe. For example, a customer maysubscribe to obtain stock quotes from a financial institution using Webservices.

Web services are provided through a number of standards. An example of aWeb services standard is Web Services Description language (WSDL). WSDL,a standard published by the World Wide Web Consortium (W3C), allows aservice provider to describe Web services in an extensible markuplanguage (XML) format as a set of endpoints operating on messages. WSDLallows endpoints and messages to be described regardless of the messageformats or network protocols.

Another Web services standard is Web services invocation framework(WSIF). WSIF is an open application programming interface (API) forinvoking Web services regardless of how the Web services are provided.Using WSIF, application developers may interact directly with abstractrepresentations of Web services through their WSDL descriptions insteadof using common message formats, such as Simple Object Access Protocol(SOAP). With these standards, Web services are widely used in electroniccommerce and business-to-business applications.

Data centers, which connect a variety of servers and devices indifferent ways, are currently managed by administrators using legacyapplications or manual operations. Many of these applications oroperations are not extensible because they are platform and programminglanguage dependent. In addition, no existing standard is present todefine data center management.

Therefore, it would be advantageous to have a standard method thatallows administrators to manage data centers regardless of languages andplatforms. It would also be advantageous to have a method and apparatusthat utilizes the benefits of Web services to facilitate communicationsbetween different types of servers and devices within a data center.

SUMMARY OF THE INVENTION

The present invention provides a method, apparatus, and computerinstructions for managing data center using Web services. The mechanismof the present invention provides two types of Web services, statelessWeb services and stateful Web services. Both of these types of Webservices allow data center administrators to manage data centeroperations. Stateless Web services include an invoker applicationprogramming interface that utilizes a Web Services Invocation Framework(WSIF) to invoke data center operations. Stateful Web services include aWSDL definition file that is associated with each data center resource,which defines attributes of the resource and data center operations.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features believed characteristic of the invention are setforth in the appended claims. The invention itself, however, as well asa preferred mode of use, further objectives and advantages thereof, willbest be understood by reference to the following detailed description ofan illustrative embodiment when read in conjunction with theaccompanying drawings, wherein:

FIG. 1 depicts a pictorial representation of a network of dataprocessing systems in which the present invention may be implemented;

FIG. 2 is a block diagram of a data processing system that may beimplemented as a server in accordance with a preferred embodiment of thepresent invention;

FIG. 3 is a block diagram of a data processing system in which thepresent invention may be implemented;

FIG. 4 is a diagram illustrating an exemplary data center in accordancewith a preferred embodiment of the present invention;

FIG. 5 is a diagram illustrating an exemplary invocation of a statelessWeb service to manager a data center resource in accordance with apreferred embodiment of the present invention;

FIG. 6 is a diagram illustrating an exemplary invocation of a statefulWeb service to manage a data center resource in accordance with apreferred embodiment of the present invention;

FIG. 7A is a diagram illustrating an exemplary implementation of theinvoker API in accordance with a preferred embodiment of the presentinvention;

FIG. 7B is a diagram illustrating an exemplary implementation of astateless Web service to reboot a switch is depicted in accordance witha preferred embodiment of the present invention;

FIG. 8 is a diagram illustrating an exemplary implementation of using astateful Web service to invoke logical device operations and retrieveresource properties is depicted in accordance with a preferredembodiment of the present invention;

FIG. 9 is a class diagram illustrating available Web services resourcesin accordance with a preferred embodiment of the present invention;

FIG. 10 is a diagram illustrating an exemplary WSDL file provided by thepresent invention in accordance with a preferred embodiment of thepresent invention;

FIG. 11 is a flowchart of a process for using stateful Web services tomanage data center resource from a client's perspective in accordancewith a preferred embodiment of the present invention; and

FIG. 12 is a flowchart of a process illustrating an exemplary process ofusing stateful Web services to manage data center resource from aserver's perspective in accordance with a preferred embodiment of thepresent invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

With reference now to the figures, FIG. 1 depicts a pictorialrepresentation of a network of data processing systems in which thepresent invention may be implemented. Network data processing system 100is a network of computers in which the present invention may beimplemented. Network data processing system 100 contains a network 102,which is the medium used to provide communications links between variousdevices and computers connected together within network data processingsystem 100. Network 102 may include connections, such as wire, wirelesscommunication links, or fiber optic cables.

In the depicted example, server 104 is connected to network 102 alongwith storage unit 106. In addition, clients 108, 110, and 112 areconnected to network 102. These clients 108, 110, and 112 may be, forexample, personal computers or network computers. In the depictedexample, server 104 provides data, such as boot files, operating systemimages, and applications to clients 108-112. Clients 108, 110, and 112are clients to server 104. Network data processing system 100 mayinclude additional servers, clients, and other devices not shown.

Furthermore, server 104 may be connected to other resources, such asrouter 130, server 114, switch 132 and storage 106. In the presentinvention, these resources in combination with network data processingsystem 100 make up a data center.

In the depicted example, network data processing system 100 is theInternet with network 102 representing a worldwide collection ofnetworks and gateways that use the Transmission ControlProtocol/Internet Protocol (TCP/IP) suite of protocols to communicatewith one another. At the heart of the Internet is a backbone ofhigh-speed data communication lines between major nodes or hostcomputers, consisting of thousands of commercial, government,educational and other computer systems that route data and messages. Ofcourse, network data processing system 100 also may be implemented as anumber of different types of networks, such as for example, an intranet,a local area network (LAN), or a wide area network (WAN). FIG. 1 isintended as an example, and not as an architectural limitation for thepresent invention.

Referring to FIG. 2, a block diagram of a data processing system thatmay be implemented as a server, such as server 104 in FIG. 1, isdepicted in accordance with a preferred embodiment of the presentinvention. Data processing system 200 may be a symmetric multiprocessor(SMP) system including a plurality of processors 202 and 204 connectedto system bus 206. Alternatively, a single processor system may beemployed. Also connected to system bus 206 is memory controller/cache208, which provides an interface to local memory 209. I/O bus bridge 210is connected to system bus 206 and provides an interface to I/O bus 212.Memory controller/cache 208 and I/O bus bridge 210 may be integrated asdepicted.

Peripheral component interconnect (PCI) bus bridge 214 connected to I/Obus 212 provides an interface to PCI local bus 216. A number of modemsmay be connected to PCI local bus 216. Typical PCI bus implementationswill support four PCI expansion slots or add-in connectors.Communications links to clients 108-112 in FIG. 1 may be providedthrough modem 218 and network adapter 220 connected to PCI local bus 216through add-in connectors.

Additional PCI bus bridges 222 and 224 provide interfaces for additionalPCI local buses 226 and 228, from which additional modems or networkadapters may be supported. In this manner, data processing system 200allows connections to multiple network computers. A memory-mappedgraphics adapter 230 and hard disk 232 may also be connected to I/O bus212 as depicted, either directly or indirectly.

Those of ordinary skill in the art will appreciate that the hardwaredepicted in FIG. 2 may vary. For example, other peripheral devices, suchas optical disk drives and the like, also may be used in addition to orin place of the hardware depicted. The depicted example is not meant toimply architectural limitations with respect to the present invention.

The data processing system depicted in FIG. 2 may be, for example, anIBM eServer™ pSeries® system, a product of International BusinessMachines Corporation in Armonk, N.Y., running the Advanced InteractiveExecutive (AIX™) operating system or LINUX operating system.

With reference now to FIG. 3, a block diagram of a data processingsystem is shown in which the present invention may be implemented. Dataprocessing system 300 is an example of a computer, such as client 108 inFIG. 1, in which code or instructions implementing the processes of thepresent invention may be located. In the depicted example, dataprocessing system 300 employs a hub architecture including a northbridge and memory controller hub (MCH) 308 and a south bridge andinput/output (I/O) controller hub (TCH) 310. Processor 302, main memory304, and graphics processor 318 are connected to MCH 308. Graphicsprocessor 318 may be connected to the MCH through an acceleratedgraphics port (AGP), for example.

In the depicted example, local area network (LAN) adapter 312, audioadapter 316, keyboard and mouse adapter 320, modem 322, read only memory(ROM) 324, hard disk drive (HDD) 326, CD-ROM driver 330, universalserial bus (USB) ports and other communications ports 332, and PCI/PCIedevices 334 may be connected to ICH 310. PCI/PCIe devices may include,for example, Ethernet adapters, add-in cards, PC cards for notebookcomputers, etc. PCI uses a cardbus controller, while PCIe does not. ROM324 may be, for example, a flash binary input/output system (BIOS). Harddisk drive 326 and CD-ROM drive 330 may use, for example, an integrateddrive electronics (IDE) or serial advanced technology attachment (SATA)interface. A super I/O (SIO) device 336 may be connected to ICH 310.

An operating system runs on processor 302 and is used to coordinate andprovide control of various components within data processing system 300in FIG. 3. The operating system may be a commercially availableoperating system such as Windows XP™, which is available from MicrosoftCorporation. An object oriented programming system, such as the Java™programming system, may run in conjunction with the operating system andprovides calls to the operating system from Java™ programs orapplications executing on data processing system 300. “JAVA” is atrademark of Sun Microsystems, Inc.

Instructions for the operating system, the object-oriented programmingsystem, and applications or programs are located on storage devices,such as hard disk drive 326, and may be loaded into main memory 304 forexecution by processor 302. The processes of the present invention areperformed by processor 302 using computer implemented instructions,which may be located in a memory such as, for example, main memory 304,memory 324, or in one or more peripheral devices 326 and 330.

Those of ordinary skill in the art will appreciate that the hardware inFIG. 3 may vary depending on the implementation. Other internal hardwareor peripheral devices, such as flash memory, equivalent non-volatilememory, or optical disk drives and the like, may be used in addition toor in place of the hardware depicted in FIG. 3. Also, the processes ofthe present invention may be applied to a multiprocessor data processingsystem.

For example, data processing system 300 may be a personal digitalassistant (PDA), which is configured with flash memory to providenon-volatile memory for storing operating system files and/oruser-generated data. The depicted example in FIG. 3 and above-describedexamples are not meant to imply architectural limitations. For example,data processing system 300 also may be a tablet computer, laptopcomputer, or telephone device in addition to taking the form of a PDA.

The present invention provides a method, apparatus, and computerinstructions for managing data centers using Web services. A data centertypically consists of many different types of servers and devices, suchas routers and switches. By using Web services, data center operationsand attributes associated with different resources may be defined in aWSDL definition file. Examples of data center operations include addinga server to a cluster of servers, removing a server from the cluster,and setting a server to maintenance mode. Some example resourceattributes include server name, server id, and server type.

The administrator may use the WSDL definition file to invoke data centeroperations on logical device operations, which provides a high-levelencapsulation to lower level operation scripts that manipulate datacenter resources. In this way, administrators may manage the data centerwithout the constraints of different platforms or programming languages.

In a preferred embodiment, the present invention provides twomechanisms, stateless Web services and stateful Web services, formanaging data center operations. Stateless Web services do not persistthe state of resources. With this type of Web services, an administratormay only invoke a data center operation on a given resource, but may notpersist the instance of the given resource for later use. The datacenter operations may be invoked using the Web services InvocationFramework (WSIF). On the other hand, stateful Web services allowadministrators to persist an instance of a given resource to not onlyinvoke data center operations on the resource, but also manipulate theattributes of the given resource and the resource's relationships withother resources.

The present invention provides stateless Web services for managing adata center through the use of an invoker application programminginterface (API). An administrator, as a Web service user, may specify anumber of input parameters for the invoke method of the invoker API toinvoke a specific data center operation. The input parameters in theillustrative examples include a WSDL definition file location, the nameof data center operation to be invoked, necessary parameters for theoperation, a user name, and a password for accessing the data centerresource. Invoker API utilizes the Web services Invocation Framework(WSIF) to invoke data center operations dynamically as specified in theWSDL file. Since stateless Web services do not persist the state of theresource, a resource id is required from the administrator each time anoperation is invoked.

For stateful Web services, the present invention allows administratorsto not only invoke data center operations on a given resource, but alsomanipulate the given resource and relationships between differentresources. With stateful Web services provided by the present invention,an administrator may access an instance of a resource in the data centerby requesting an endpoint reference for the given resource using aproperty, such as a resource name. As used herein, an endpoint referenceis the end location of a particular resource, which is normallyrepresented in the form of a Uniform Resource Identifier (URI) or aUniform Resource Locator (URL). The administrator may then add theendpoint reference to a Simple Object Access Protocol (SOAP) header,such that the endpoint reference may later be used for subsequentrequests. Once the endpoint reference is set, the resource is persistentwithin the scope of the Web services session. At this time, theadministrator may retrieve or set any property associated with theresource and invoke logical device operations to manipulate thatresource.

Turning now to FIG. 4, a diagram illustrating an exemplary data centeris depicted in accordance with a preferred embodiment of the presentinvention. As shown in FIG. 4, in this illustrative example, data center400 includes resources, such as, customer 402, server 404, Virtual LocalArea Network (VLAN) 406, subnet 408, router 410, switch 412, softwareproducts 416, load balancer 418, and data container 420.

Customer 412 may be, for example, a client or an administrator who usesa data processing system, such as data processing system 300 in FIG. 3.Server 404 may be implemented as a data processing system, such as dataprocessing system 200 in FIG. 2. Server 404 may also be implemented asan application server, which hosts Web services, or other types ofservers. Router 410 and switch 412 facilitate communications betweendifferent devices. VLAN 406 is a network of computers that behave as ifthey are connected to the same wire even though they may actually bephysically located on different segments of a local area network. Subnet408 is a portion of a network, which may be a physically independentnetwork segment and shares a network address with other portions of thenetwork.

Software products 416 are applications that may be executed on a clientor a server. Load balancer 418 spreads task among multiple systems suchthat no single system is overwhelmed. Load balancer 418 is normallyimplemented as software running on a data processing system. Datacontainer 420 may be a database, such as DB2 Universal Database, aproduct available from International Business Machines Corporation.

Data center 400, as depicted in FIG. 4, is presented for purposes ofillustrating the present invention. Other resources, such as, forexample, cluster of servers and switch port, also may be included indata center 400.

Turning now to FIG. 5, a diagram illustrating an exemplary invocation ofa stateless Web service to manager a data center resource is depicted inaccordance with a preferred embodiment of the present invention. Asshown in FIG. 5, in this illustrative example, when client 500 wants toperform a data center operation on a resource, client 500 invokes clientapplication 502, which may be a Web service interface, to call invokemethod 504 of the invoker API provided by the present invention. Theinvoker API allows client 500 to invoke stateless Web services on server508.

When calling invoke method 504, client 500 submits input parameters,which include the location of WSDL file 510, the desired operation name,parameters necessary for the operation, a user name and password foraccess to the resource. WSDL file 510 defines resources, theirattributes, and a set of operations that the data center administratorcan perform on the resources.

Using the user name and password submitted by client 500, the identityof the administrator may be authenticated before access of data centerresource is allowed. Once the identity of the administrator isauthenticated, instance of the resource, Web service 506, is locatedusing WSDL file 510 and logical data operation 514 is invoked by Webservices 506 to run lower level workflow scripts 516. Workflow scripts516 in turn perform data center operation on the resource in data center520.

In this illustrative example, the present invention allows theadministrator to invoke a stateless Web service to perform data centeroperation on a given resource. However, the administrator is unable tomanipulate attributes of the given resource, since the state of theresource is not persistent.

Turning now to FIG. 6, a diagram illustrating an exemplary invocation ofa stateful Web service to manage a data center resource is depicted inaccordance with a preferred embodiment of the present invention. Asdepicted in FIG. 6, in this illustrative example, when client 600 wantsto invoke a data center operation on a resource, client 600 firstinvokes client application 602 to access an instance of this resourcefrom server 601. Client application 602 accesses the instance byretrieving an endpoint reference of the resource from WSDL file 603(call 606). The endpoint reference is retrieved by using a resourceproperty, such as a server name. Once the instance of the resource, Webservices 604, is accessed, the endpoint reference is returned to clientapplication 602 in a SOAP element (call 608).

When the endpoint reference is received by client application 602,client application 602 sets the endpoint reference in a property of theSOAP stub (call 610). In addition, SOAP client handler 611 sets theendpoint reference to the SOAP message header, such that subsequentrequests through the stub may re-use the same endpoint reference (call612). Once the endpoint reference is set in the SOAP header, theresource is now persistent within the scope of the current Web servicessession and client 600 may access the instance of the resource to invokea data center operation or retrieve properties for the resource (call614).

After a data center operation is invoked by client 500 via clientapplication 602, SOAP server handler 618 writes the endpoint referenceto a SOAP message context (call 616) for Web services 604 to extract(call 620). When the endpoint reference is extracted, a resource id isretrieved from the message context which identifies a particularresource in the data center to invoke the operation on. After theresource id is retrieved, Web services 604 calls logical deviceoperations 624, which is a high-level encapsulation of lower levelworkflow scripts to perform a specific data operation (call 622). Thelogical device operations 624 run lower level workflows scripts (call626) to manage resource of data center 630 accordingly (call 628).

Thus, using the stateful Web services, an administrator is able toaccess the instance of a given resource, such that the administrator maycreate or destroy the instance at any time. In addition, theadministrator also may retrieve or set attributes for the givenresource, interrogate relationships associated with the given resourceand invoke data center operations on the given resource. Furthermore,there is no need for the client to submit a resource ID each time, as inthe case of stateless Web services, as an input parameter to the Webservice, because the state of the resource is now persistent.

Turning now to FIG. 7A, a diagram illustrating an exemplaryimplementation of the invoker API is depicted in accordance with apreferred embodiment of the present invention. As shown in FIG. 7A, inthis illustrative example, the invoker API 700 includes an invoke method702, which takes in five input parameters: wsdlLocation 704,operationName 706, params 708, username 710, and password 712.

WsdlLocation 704 defines the WSDL file location for the Web service thatis to be invoked by the client. OperationName 706 defines the name ofthe data center operation to be invoked. Params 708 defines one or moreparameters to be passed into the operation. Username 710 and password712 define the userid and password required for authentication of anadministrator in order to access the data center resource. Thus, usinginvoke method 702 of the invoker API 700, an administrator maydynamically invoke data center operations on a given resource.

Turning now to FIG. 7B, a diagram illustrating an exemplaryimplementation of a stateless Web service to reboot a switch is depictedin accordance with a preferred embodiment of the present invention. Asshown in FIG. 7B, in this illustrative example, an administratorspecifies the location of the WSDL file 740 in a URL or URI format.

The administrator then specifies the operation as a “reboot” operation742 and a device id of “33333” 744 to be included in the list ofparameters 746 for the “reboot” operation. Once the input parameters areset, the administrator then invokes the invoke method, such as invokemethod 702 in FIG. 7A, and passes in the input parameters.

In this illustrative examples the administrator wants to reboot a switchwith a device id of “33333”. By specifying the WSDL file locationdirectly, the present invention allows the operation to be invoked on aspecific switch.

Turning now to FIG. 8, a diagram illustrating an exemplaryimplementation of using a stateful Web service to invoke logical deviceoperations and retrieve resource properties is depicted in accordancewith a preferred embodiment of the present invention. As shown in FIG.8, in this illustrative example, client application 800 may query aserver for an endpoint reference of a desired resource. A server name of“IBM WAS Server” 802 is used. The endpoint reference is retrieved byinvoking a findReferenceByProperties method 804. Next, the client addsthe endpoint reference to a SOAP header by setting the endpointreference in the property of the SOAP stub 806. Once the endpointreference is set in the SOAP header, the administrator may access theserver resource instance and retrieve attributes of the resourceaccordingly.

In this illustrative example, the administrator accesses the attributesby invoking a getResourceProperty method 808 to retrieve the serveridentifier 810, isFailed 812, the TCP port number 814, and the pool name816. In addition to retrieving the attributes, the administrator mayalso set attributes, define relationships between this resource andother resources, and invoke logical device operations to physicallymanipulate the server resource in the data center.

In this depicted example, the administrator may set the serverresource's maintenance mode to true by invoking a setMaintenance method818, which means no one has access to the server resource other than theadministrator. The administrator also adds the server resource to acluster by invoking the addServer method 820. At any time, theadministrator may query the status of a request by invoking agetRequestStatus method to determine whether the Web service sessionshould be terminated or whether to destroy the instance of the serverresource.

Turning now to FIG. 9, a class diagram illustrating available Webservices resources is depicted in accordance with a preferred embodimentof the present invention. As depicted in FIG. 9, On demandinfrastructure (ODI) services are web services and infrastructures thatsupport business on demand in an enterprise computing environment, ODIservice class 900 is a base class that includes a number of defaultmethods. These methods include lock 902, unlock 904, get resourceproperty 906, get multiple resource properties 908, set resourceproperties 910, query resource properties 912, associate relationship914, de-associate relationship 916, find relationship types 918, getrelationship endpoint reference (EPR) by type 920, find references byproperties 922, assign 924 and unassign 926.

ODI service 900 is inherited by a number of subclasses, which areavailable resources in the data center. These resources includeApplication service 932, server service 934, application tier service936, customer service 938, fibre channel (FC) fabric service 940, routerservice 942, storage area network (SAN) frame service 944, softwareproducts service 946, software stack service 948, storage pool service950, sub-network service 952, switch port service 954, switch service956. VLAN service 958 and volume manager service 960, Applicationservice 932 provides Web services operations to manipulate theapplication resource of the data center and server service 934 providesWeb services operations to manipulate the server resource of the datacenter, etc.

Services 932-960 inherit default methods 902-926 from ODI service 900,such that an administrator may manipulate services 932-960 once aninstance of the resource is obtained. For example, lock method 902allows the administrator to lock a resource. Unlock method 904 allowsthe administrator to unlock the resource.

Get resource property method 906 allows the administrator to retrieve anattribute of a resource by the property name, for example,NumberOfBlocks. Get multiple resource properties method 908 retrievesthe value of an attribute by a list of property names, for example,NumberOfBlocks and Size. Set resource properties 910 sets a number ofattributes by inputting an XML string. Query resource properties method912 allows an administrator to query attributes by specifying acondition. For example, an administrator may NumberOfBlocks>20 andBlockSize=1024. Associate relationship method 914 associates tworesources with a given relationship type and de-associate relationshipmethod 916 undo the association. For example, a customer resource may beassociated with an application resource with a relationship type of“OWN”, since the customer may own an application.

Find relationship types method 918 finds relationship types for a givenresource based on all possible relationship types for the resourceregardless of whether or not the relationship types are associated withother resources. Get relationship EPR by type method 920 gets therelationship endpoint references by type. Find references by propertiesmethod 922 finds the list endpoint references that are associated with agiven resource properties. This is the method invoked by theadministrator in order to access an instance of a resource. Assignmethod 924 assigns and unassign method 926 unassigns a given resource toan application. Thus, default methods 902-926 enable the administratorto manipulate the attributes of data center services using propertiesspecified the WSDL definition file.

In addition to default methods 902-926 inherited from ODI service 900,server service 934 also includes customized methods, such as serverevent 927, admin server event 928, and set maintenance 929. Server eventmethod 927 allows an administrator to set the server failure status toeither true or false. Admin server event 928 allows the administrator toset the admin server failure status to either true or false. Setmaintenance method 929 allows the administrator put a server resource inmaintenance mode by setting it to true or take a server resource out ofmaintenance mode by setting it to false. As to application tier service936, customized methods, such as allocate server and remove server areprovided for an administrator to add a server to or remove a server froma cluster.

In this manner, the present invention provides a set of Web servicesthat allows the administrator to manipulate attributes of any givenresource in a data center. Other resources may also be provided byinheriting ODI service 900.

Turning now to FIG. 10, a diagram illustrating an exemplary WSDL fileprovided by the present invention is depicted in accordance with apreferred embodiment of the present invention. As depicted in FIG. 10,WSDL file 1000 adheres to the standard of Web Services DefinitionLanguage (WSDL). In the schema section 1001, a number of common 1002 andserver resource properties 1004 are defined. Common resource propertiesare shared by all data center resources and server resource propertiesare specific to a server resource. Examples of common property includean identifier 1006 and a name of the resource 1008. Examples of serverresource properties include isMaintenance 1010 and isFailed 1012.

In addition to resource properties, the schema section of WSDL file 1000also defines a number of data elements that will be used by WSDLmessages. Subsequent to the schema section, a number of WSDL messagedefinitions 1014 are provided to define data elements of data centeroperation. Each message includes one or more parts. A message can becompared to an input or output of a function, which contains one or moreparts, which are input or output parameters. Examples of messagesinclude ‘assign request’ 1016 and ‘assign response’ 1018. Each messagerepresents an input and output of the ‘assign’ operation.

After the messages are defined, a set of operations are defined usingthe defined messages. For example, operation ‘assign’ 1020 is definedwith an input of ‘assign request’ 1022 and an output of ‘assignresponse’ 1024. Operation ‘assign’ may be compared to a function of aprogram in traditional programming, except in this example, ‘assign’ isan operation provided by a resource, such as a server resource. Theseoperations represent default methods and customize methods as describedin FIG. 9. Once operations are defined, WSDL file 1000 defines a Webservice to include all defined operations. In this example, ‘serverservice service’ 1026 is defined to include the operations.

Turning now to FIG. 11, a flowchart of a process for using stateful Webservices to manage data center resource from a client's perspective isdepicted in accordance with a preferred embodiment of the presentinvention. As depicted in FIG. 11, in this illustrative example, aclient wants to access a server resource from the data center. Theprocess begins when the client application sets a server name in aresource property (step 1102). The client application may use anyresource property to obtain an endpoint reference. However, since aserver name is unique to each server, using the server name propertywill locate only a single server from the data center. Next, the clientapplication converts the resource property to an XML string (step 1104).

Once the resource property is converted, the client application invokesthe findReferenceByProperties method to obtain endpoint reference of theserver resource (step 1106). After the EPR is obtained, the clientapplication sets the EPR in the SOAP header for future use (step 1108).The server resource is now persistent within the scope of the Webservices session and the client application may access the instancethroughout the resource lifecycle.

The client application may invoke operations that are defined in theWSDL file, such as WSDL file 900 in FIG. 9, to manipulate the serverresource (step 1110). Examples of data center operations include add aserver to a cluster, remove a server from a cluster, and set the servermaintenance mode to true. The client application also may retrieve orset a number of server resource attributes, such as server identifierand server type. Once the operation is complete, a determination is thenmade by the client application as to whether to perform additionaloperations (step 1112). If additional operations are to be performed,the client application returns to step 1110 to invoke another WSDLdefined operations to further manipulate the resource.

If no additional operations are to be performed, the client applicationinvokes the get request status method (step 1114) and make adetermination as to whether all outstanding requests are complete (step1116). If all requests are complete, the client application terminatesthe current Web services session (step 1118) and destroys the resourceinstance (step 1120). Thus, the process terminates thereafter.Otherwise, the process returns to step 1116 until all outstandingrequests are complete.

Turning now to FIG. 12, a flowchart of a process illustrating anexemplary process of using stateful Web services to manage data centerresource from a server's perspective is depicted in accordance with apreferred embodiment of the present invention. As depicted in FIG. 12,in this depicted example, the process begins when server, such as server601 in FIG. 6, receives a request from the client for an endpointreference of a resource (step 1202). The server returns a SOAP elementwith an endpoint reference for the desired resource (step 1204). Later,the server receives a data center operation request on the resource(step 1206). The server then obtains the endpoint reference from theSOAP header (step 1208) and invokes the logical device operation (LDO)with a device ID (step 1210).

The LDO provides a high level view of device operations that a clientcan run. For example, a ‘cluster.AddServer’ LDO provides a baseinterface that the client can use to add a server to a cluster. Theserver then calls workflows associated with the particular resource(step 1212). Workflows provide detail implementation of the baseinterface. A client may associate a LDO with workflows for a givendevice or resource. When the client invokes an LDO with a device ID, asin this example, the server determines which workflows are associatedwith the LDO. In the present invention, a workflow may call otherworkflow to perform specific operations. Each workflow also contains lowlevel scripts that are used to manipulate the data center. Finally, theserver calls a workflow for the device to perform operation on theresource in the data center (step 1214) with the process terminatingthereafter.

In summary, the present invention provides a platform and languageindependent method for managing data centers by using Web services. Thepresent invention recognizes the deficiencies of current solutions formanaging data centers and provides both stateless and stateful Webservices solutions. With the use of stateful Web services, anadministrator may use a standard Web services interface to remotelyaccess a resource in a data center without accessing the actual device.With the benefits of Web services standards, such as WSDL, the presentinvention enables the administrator to manage resources of the datacenter more efficiently, because the administrator may use differenttypes of Web based applications, such as hypertext markup language(HTML) and Java server pages (JSP), to access the resource. Furthermore,stateful Web services provide the administrator a way to manageresources based on a specific resource instance. The present inventionmay also define how long a client or administrator may access aparticular resource instance.

It is important to note that while the present invention has beendescribed in the context of a fully functioning data processing system,those of ordinary skill in the art will appreciate that the processes ofthe present invention are capable of being distributed in the form of acomputer readable medium of instructions and a variety of forms and thatthe present invention applies equally regardless of the particular typeof signal bearing media actually used to carry out the distribution.Examples of computer readable media include recordable-type media, suchas a floppy disk, a hard disk drive, a RAM, CD-ROMs, DVD-ROMs, andtransmission-type media, such as digital and analog communicationslinks, wired or wireless communications links using transmission forms,such as, for example, radio frequency and light wave transmissions. Thecomputer readable media may take the form of coded formats that aredecoded for actual use in a particular data processing system.

The description of the present invention has been presented for purposesof illustration and description, and is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the art. Theembodiment was chosen and described in order to best explain theprinciples of the invention, the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated.

1. A method in a data processing system for managing a data center, themethod comprising: receiving a user input to invoke an operation on aresource in the data center, wherein the user input identifies theoperation and a Web service for performing the operation; and initiatingthe operation on the resource in the data center using the Web serviceidentified in the user input.
 2. The method of claim 1, wherein the Webservice is a stateless Web service in which an identification of aresource is required each time a selected operation is invoked on theresource.
 3. The method of claim 1, wherein the Web service is astateful Web service in which an identification of the resource ispersisted for subsequent invocation of operations on the resource. 4.The method of claim 1, wherein the user input is received at aninterface for the Web service.
 5. The method of claim 4, wherein theuser input includes a Web services description language file location,an operation name, and operation parameters.
 6. The method of claim 1,wherein the user input includes an identification of a Web servicedescription language file and wherein the initiating step includes:invoking the operation on the resource in a manner specified in the Webservice description language file.
 7. The method of claim 1, whereinresources in the data center includes at least one of a server, acluster of servers, and a virtual local area network.
 8. The method ofclaim 1, wherein resources in the data center further includes at leastone of a switch, a router, a balancer, software products, and a datacontainer.
 9. A method for performing operations on a resource in a datacenter, the method comprising: detecting a request to invoke anoperation on the resource in the data center from a data processingsystem, wherein the request includes an identification of a Web service;and invoking the operation from a plurality of logical device operationsto perform a logical device operation on the resource using theidentification of the Web service.
 10. The method of claim 9, whereinthe identification of the Web service is an endpoint reference of theWeb service.
 11. The method of claim 9, wherein the request includes aWeb services description language file and wherein the Web servicesdescription language file defines attributes and operations of theresource in the data center.
 12. The method of claim 9, wherein theplurality of logical device operations includes adding a server resourceto a cluster, removing a server resource from a cluster, setting theresource in maintenance, associating the resource with another resource,and disassociating the resource from another resource.
 13. The method ofclaim 9, wherein invoking the operation from the plurality of logicaldevice operations includes invoking workflows associated with theresource, and wherein the workflows includes low level scripts thatphysically manipulate the resource in the data center.
 14. A dataprocessing system for managing a data center, the data processing systemcomprising: receiving means for receiving a user input to invoke anoperation on a resource in the data center, wherein the user inputidentifies the operation and a Web service for performing the operation;and initiating means for initiating the operation on the resource in thedata center using the Web service identified in the user input.
 15. Thedata processing system of claim 14, wherein the Web service is astateless Web service in which an identification of a resource isrequired each time a selected operation is invoked on the resource. 16.The data processing system of claim 14, wherein the Web service is astateful Web service in which an identification of the resource ispersisted for subsequent invocation of operations on the resource. 17.The data processing system of claim 14, wherein the user input isreceived at an interface for the Web service.
 18. The data processingsystem of claim 17, wherein the user input includes a Web servicesdescription language file location, an operation name, and operationparameters.
 19. A data processing system for performing operations on aresource in a data center, the data processing system comprising:detecting means for detecting a request to invoke an operation on theresource in the data center from a data processing system, wherein therequest includes an identification of a Web service; and invoking meansfor invoking the operation from a plurality of logical device operationsto perform a logical device operation on the resource using theidentification of the Web service.
 20. The data processing system ofclaim 19, wherein the identification of the Web service is an endpointreference of the Web service.
 21. The data processing system of claim19, wherein the request includes a Web services description languagefile and wherein the Web services description language file definesattributes and operations of the resource in the data center.
 22. Thedata processing system of claim 19, wherein the plurality of logicaldevice operations includes adding a server resource to a cluster,removing a server resource from a cluster, setting the resource inmaintenance, associating the resource with another resource, anddisassociating the resource from another resource.
 23. The dataprocessing system of claim 19, wherein invoking means includes means forinvoking workflows associated with the resource, and wherein theworkflows includes low level scripts that physically manipulate theresource in the data center.
 24. A computer program product in acomputer readable medium for managing a data center, the computerprogram product comprising: first instructions for receiving a userinput to invoke an operation on a resource in the data center, whereinthe user input identifies the operation and a Web service for performingthe operation; and second instructions for initiating the operation onthe resource in the data center using the Web service identified in theuser input.
 25. The computer program product of claim 24, wherein theWeb service is a stateless Web service in which an identification of aresource is required each time a selected operation is invoked on theresource.
 26. The computer program product of claim 24, wherein the Webservice is a stateful Web service in which an identification of theresource is persisted for subsequent invocation of operations on theresource.
 27. The computer program product of claim 24, wherein the userinput is received at an interface for the Web service.
 28. The computerprogram product of claim 27, wherein the user input includes a Webservices description language file location, an operation name, andoperation parameters.
 29. The computer program product of claim 24,wherein the user input includes an identification of a Web servicedescription language file and wherein the second instructions includes:sub-instructions for invoking the operation on the resource in a mannerspecified in the Web service description language file.
 30. The computerprogram product of claim 24, wherein resources in the data centerincludes at least one of a server, a cluster of servers, and a virtuallocal area network.
 31. The computer program product of claim 24,wherein resources in the data center further includes at least one of aswitch, a router, a balancer, software products, and a data container.32. A computer program product for performing operations on a resourcein a data center, the computer program product comprising: firstinstructions for detecting a request to invoke an operation on theresource in the data center from a data processing system, wherein therequest includes an identification of a Web service; and secondinstructions for invoking the operation from a plurality of logicaldevice operations to perform a logical device operation on the resourceusing the identification of the Web service.
 33. The computer programproduct of claim 32, wherein the identification of the Web service is anendpoint reference of the Web service.
 34. The computer program productof claim 32, wherein the request includes a Web services descriptionlanguage file, and wherein the Web services description language filedefines attributes and operations of the resource in the data center.35. The computer program product of claim 32, wherein the plurality oflogical device operations includes adding a server resource to acluster, removing a server resource from a cluster, setting the resourcein maintenance, associating the resource with another resource, anddisassociating the resource from another resource.
 36. The computerprogram product of claim 32, wherein the second instructions includessub-instructions for invoking workflows associated with the resource,and wherein the workflows includes low level scripts that physicallymanipulate the resource in the data center.
 37. A data processing systemcomprising: a bus system; a memory connected to the bus system, whereinthe memory includes a set of instructions; and a processing unitconnected to the bus system, wherein the processing unit executes a setof instructions to receive a user input to invoke an operation on aresource in the data center, wherein the user input identifies theoperation and a Web service for performing the operation; and initiatethe operation on the resource in the data center using the Web serviceidentified in the user input.
 38. A data processing system comprising: abus system; a memory connected to the bus system, wherein the memoryincludes a set of instructions; and a processing unit connected to thebus system, wherein the processing unit executes a set of instructionsto detect a request to invoke an operation on the resource in the datacenter from a data processing system, wherein the request includes anidentification of a Web service; and invoke the operation from aplurality of logical device operations to perform a logical deviceoperation on the resource using the identification of the Web service.